Quality Assurance
QAs as are the arbiters of quality for a project. They are responsible for making sure that projects and codebases are of a high quality and that after a ticket has been completed. If a project is buggy it is their responsibility to make sure that bugs get fixed.
RACI (Responsible, Accountable, Consulted, Informed)
Below is a list of activities that the this role is accountable for being completed. It is worth noting, that this doesn't mean this role has to do all of these things themselves, but they are accountable for ensuring that they are done.
- Record bugs in the project management board when found
- Confirm that tickets have been completed compared to the specification on tickets written by Project Managers
- Ensure that the quality of the code in the codebase is high
- Manually test the product to make sure it works
- Writing documentation
- Ensure accurate logging is added to all scripts
Tips
- You are there to guide the other engineers to writing great code
- Be sure to keep track of bugs on your Kanban Board
Common Pitfalls
Lots of people run into the same issue with this role, for example
- Not testing all of the edge cases for software (e.g. what happens if I enter
(*£&!(!))into this email box?) - Getting annoyed at Engineers for writing buggy code, help them to fix it instead
- When reporting tickets, give as much information as you can to be able to reproduce it